✅ Deploy Preview for cedarjs ready!

Name	Link
🔨 Latest commit	a731912
🔍 Latest deploy log	https://app.netlify.com/projects/cedarjs/deploys/69ea0f8c5ba7650008a3e72c
😎 Deploy Preview	https://deploy-preview-1663--cedarjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Greptile Summary

This PR advances the Universal Deploy (UD) integration through phases 2–4: it introduces buildCedarDispatcher (rou3-based routing over Fetch-native handlers), a cedarDevDispatcherPlugin that replaces the old cedarWaitForApiServer middleware so standard Cedar apps no longer spawn a separate API process during dev, a cedarUniversalDeployPlugin for Vite builds, and wires cedar build api / cedar serve api to emit and launch the self-contained srvx entry at api/dist/ud/index.js.

The previously flagged race condition in the dev dispatcher (stale cachedDispatcher overwrite) has been addressed with a generation counter. The ALL_HTTP_METHODS coverage for non-GraphQL routes is correct.

Confidence Score: 5/5

Safe to merge; all remaining findings are P2 doc/style suggestions with no blocking logic errors.

Prior P1 concerns (race condition, ALL_HTTP_METHODS coverage) are resolved in this PR. The two open items are P2: a minor port-exclusion gap in the custom-server dev lane (unlikely in practice), and stale entries in the project overview doc.

docs/implementation-docs/2026-03-26-cedarjs-project-overview.md (DEV/BUILD section), packages/cli/src/commands/dev/devHandler.ts (web port exclusion)

Important Files Changed

_{Reviews (12): Last reviewed commit: "review fixes" | Re-trigger Greptile}

🤖 Nx Cloud AI Fix

Ensure the fix-ci command is configured to always run in your CI pipeline to get automatic fixes in future runs. For more information, please see https://nx.dev/ci/features/self-healing-ci

View your CI Pipeline Execution ↗ for commit a731912

☁️ Nx Cloud last updated this comment at 2026-04-23 12:58:28 UTC

@greptileai you said "This PR adds Phase 2 of the Universal Deploy integration". What's left to do for Phase 3, to also be able to include that in this PR?

According to the implementation plan, Phase 3's exit criteria are:

1. Cedar can run in production on Node without Fastify — the createUDServer (srvx-based) covers this for the standalone UD server, but the plan specifically calls for @universal-deploy/adapter-node to be the mechanism, not a custom srvx server.

2. Cedar's server entries registered in the UD store at build time — the Vite plugin does call addEntry(), but the virtual module it returns is a 501 stub:

   // vite-plugin-cedar-universal-deploy.ts
   return new Response(
     'Cedar API virtual entry: not yet implemented (Phase 5)',
     { status: 501 },
   )

   This needs to be replaced with a real Fetchable that dispatches to the discovered Cedar API functions.

3. yarn cedar serve no longer depends on Fastify — not addressed yet.

So concretely, what's left:

• Replace the 501 stub in vite-plugin-cedar-universal-deploy.ts's load() with a real Cedar API dispatcher. The route discovery logic already exists in createUDServer.ts — the pieces are there, they just need to be wired into the virtual module's fetch handler.
• Validate @universal-deploy/adapter-node end-to-end (the plan calls this out explicitly as a Phase 3 deliverable).
• Wire yarn cedar serve to delegate to the UD node adapter rather than Fastify.

The plan notes that Phase 3's real Fetchable implementation depends on the Phase 2 route manifest — which is partly why the PR punted it to Phase 5. But since Phase 2 route discovery is also in this PR (createUDServer handles it at runtime), you have enough to at least make the virtual module non-stub and do the end-to-end validation.